Skip to content

Conversation

@Jipperism
Copy link
Collaborator

No description provided.

- Introduced a new component to present a list of orchestrators with their voting statistics, including proposals voted on, votes casted, recent votes, and voting turnout.
- Added Cube.js client for data fetching with new utility functions for querying voting history.
- Introduced VotingHistoryView component to display voting statistics, including proposals voted on and voting turnout.
- Updated package.json and pnpm-lock.yaml to include Cube.js client dependencies.
- Exported VoterSummary type for better type management in voting components.
- Integrated VotingHistoryView into the account layout for displaying voting statistics.
- Added new VotingHistory page to handle routing and data fetching for user voting history.
- Updated account layout to include a new tab for voting history, improving user navigation.
- Implemented utility functions for processing and summarizing voting data from Cube.js.
- Added OrchestratorVotingList component to display voting data for orchestrators.
- Implemented tabbed interface for Yield Overview and Voting History sections.
- Integrated voter summary processing functions to aggregate voting data.
- Updated getStaticProps to fetch and pass initial voter data to the page.
- Adds treasury proposals voting overview
@Jipperism Jipperism linked an issue Dec 22, 2025 that may be closed by this pull request
@vercel
Copy link

vercel bot commented Dec 22, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
explorer-arbitrum-one Ready Ready Preview, Comment Jan 9, 2026 7:14pm

- Changed the method of accessing raw data from Cube.js API to use a function call.
- Simplified response validation in getStaticProps by removing unnecessary checks and directly using the response for voter summaries.
- Fetches voting metrics (voted/eligible) from Cube.js using LivepeerVoteProposals
- Adds an interactive Stat card to OrchestratingView with a visual progress bar
- Displays participation rate percentage and integrated link to account history
- Adds  utility to the Cube query generator
…nology

- Moved to a friendlier "Sky & Tomato" color scheme to keep voting separate from our main green brand accent.
- Standardized labels to "For / Against / Abstain" everywhere, including the global transaction feed.
- Rebuilt the vote table using our core data table component for a consistent look.
- Made it easier to explore voter history with new dedicated buttons, better tooltips, and subtle animations.
- Cleaned up the layout by stripping out redundant titles and shrinking fonts where they were getting too loud.
- Polished the details: added specific styling for "No reason provided" and refined how voter profiles are we showing voter names and txn links.
- Eliminated the agent log useEffect that was posting debug information.
- Streamlined imports by removing unnecessary useEffect import.
…List

- Changed badge colors to use a "Sky & Tomato" color scheme for better visual distinction.
- Updated badge labels from "Yes/No" to "For/Against" to standardize terminology across the application.
- Enhance typography hierarchy and spacing in the 'Your vote' section.
- Implement translucent button styles with high-contrast labels and subtle borders.
- Improve progress bar visibility and color contrast for better scannability.
- Adjust voting reason input for improved visual balance and focus states.

Fixes #464
@rickstaa
Copy link
Member

rickstaa commented Jan 8, 2026

@thebeyondr, @Jipperism the subgraph changes have been deployed under v1.3.0 which the explorer should have automatically switched to. As a result you can now get all data easily using the subgraph. You can see the new schema here.

- Eliminated the 'Voting History' tab from the account layout.
- Removed related imports and conditional rendering for improved code clarity.
- Introduced GraphQL queries for fetching treasury vote events and vote events.
- Implemented corresponding React hooks for easy integration in components.
- Enhanced the data structure to include relevant fields such as proposal details and voter information.
- Added functionality to fetch and display treasury vote events and vote events in the HistoryView component.
- Enhanced data handling with hooks to manage and extend event data, including proposal details and attributes.
- Updated rendering logic to accommodate new event types and improve user experience with detailed information on votes.
@Jipperism
Copy link
Collaborator Author

Jipperism commented Jan 9, 2026

Thanks @rickstaa , the new graphql is much cleaner than the solution we had.

@rickstaa
Copy link
Member

rickstaa commented Jan 9, 2026

Thanks @rickstaa , the new graphql is much cleaner than the solution we had.

Great to hear it improves the codebase. I did not tackle this in the past as the RPC solution was suboptimal.

@rickstaa
Copy link
Member

rickstaa commented Jan 9, 2026

@ECWireless keep in mind that its best to wait till the subgraph is fully indexed before merging this. You can see the status of v1.3.0 here.

image

I however think the UI/UX reviews will take a couple of days also so should not be a problem with this one.

@rickstaa
Copy link
Member

rickstaa commented Jan 9, 2026

@ECWireless keep in mind that its best to wait till the subgraph is fully indexed before merging this. You can see the status of v1.3.0 here.

image I however think the UI/UX reviews will take a couple of days also so should not be a problem with this one.

O looks like the UI was lagging and it is synced now.

image

@Jipperism Jipperism force-pushed the 310-showcase-orchestrator-voting-activity-in-the-ui branch from a2a6b90 to c63e205 Compare January 9, 2026 16:58
- Deleted the Cube.js client and associated query generator as their functionality has been replaced by direct GraphQL queries.
- Updated components to utilize new treasury proposal and vote queries, enhancing data fetching and management.
- Refactored the OrchestratingView component to integrate treasury votes and proposals directly through Apollo hooks.
@Jipperism Jipperism force-pushed the 310-showcase-orchestrator-voting-activity-in-the-ui branch from c63e205 to fa784c5 Compare January 9, 2026 16:59
- Updated the TreasuryVotesQuery to include the voter ID for better data management.
- Integrated ENS name fetching for voters in the VoteTable component, improving user experience.
- Refactored vote rendering logic in DesktopVoteTable and MobileVoteTable to utilize the new voting support mapping.
- Enhanced error handling in VoteTable to display error messages more clearly.
- Improved overall data structure and state management for votes and events.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Showcase orchestrator voting activity in the UI

4 participants